feat(analytics): app-scoped analytics read endpoint (2/3) - #2192

The data slice scoped the fresh-stack runner to its own suites; now
that integration.test.ts and million.test.ts exist in this tree,
re-extend the default path and restore the --million entrypoint and
its package script.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Follows up 2191's action_v3_stats_daily -> action_legacy_stats_daily
rename: the field name and alias in get-world-id-analytics.graphql,
the endpoint's literal refs and hasV3History/has_v3_history naming,
and every test call site (integration.test.ts, million.test.ts,
world-id-analytics.test.ts). Regenerated the operation's generated.ts.

Also fixes a real bug the rename exposed: integration.test.ts's
tracked-table discovery regex hardcoded action_v[34]_stats_daily,
so it silently stopped matching the renamed table. Broadened to
action_(?:legacy|v4)_stats_daily.

Verified: tsc, prettier, unit 26/26, fresh-stack smoke+backfill+
integration 29/29, million gate 1/1 (1M-row backfill+catchup+parity).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

The cron route now reports distinct outcomes and advances at most 30
days per tick, so the integration assertions pin the exact outcome
(advanced vs lock_missed) instead of a bare success body, and the
million gate's initial 31-day backfill follows the production runbook
through backfill_world_id_analytics(1) while the catch-up tick keeps
exercising the capped route.

Evidence on this tree: fresh-stack default runner green (data-slice
suites + integration 19/19), million gate green - 1M-row chunked
backfill 506ms, catch-up 42ms, endpoint p95 ~29ms/24ms both periods.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

… failing it

Merge-forward of the parent-lock fix: with the rollup pre-locking its
parent actions, a mid-chunk deletion queues on the parent (previously it
deadlocked as the 40P01 victim, and this test's old choreography let it
slip through only because a first-ever rollup locks no child rows). The
chunk now completes, the deletion cascades after, and a re-roll of the
range stays empty.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>